Skip to content

feat: additional envars for customization#855

Open
krishnaGajabi wants to merge 1 commit into
openebs:developfrom
krishnaGajabi:develop
Open

feat: additional envars for customization#855
krishnaGajabi wants to merge 1 commit into
openebs:developfrom
krishnaGajabi:develop

Conversation

@krishnaGajabi
Copy link
Copy Markdown
Contributor

Description

Addition of following envvars for customization

TCP OPTS
NVMF_TCP_IN_CAPSULE_DATA_SIZE 4096
NVMF_TCP_MAX_IO_SIZE 131072
NVMF_TCP_IO_UNIT_SIZE 131072

RDMA OPTS
NVMF_RDMA_DATA_WR_POOL_SIZE 4095
NVMF_RDMA_MAX_IO_SIZE 131072
NVMF_RDMA_IO_UNIT_SIZE 8192
NVMF_RDMA_IN_CAPSULE_DATA_SIZE 4096

Motivation and Context

Users can custiomize installation according to there environment needs for optimised performance.

How Has This Been Tested?

Deployed chart on a 3 worker node cluster.
Checked the default values
did a in place upgrade and modified tcp opts, changes were reflected
did a in place upgrade after enabling rdma and changes were refelected in daemonset

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • [x ] New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • [ x] My code follows the code style of this project.
  • [ x] My change requires a change to the documentation.
  • [ x] I have updated the documentation accordingly.
  • I have added unit tests to cover my changes.

Signed-off-by: krishnaGajabi <gajbikrishna23@gmail.com>
@krishnaGajabi krishnaGajabi requested a review from a team as a code owner May 19, 2026 11:42
Comment thread chart/values.yaml
Comment on lines +504 to +510
# -- RDMA data WR pool size (RDMA only)
dataWrPoolSize: "4095"
# -- Max number of in-capsule data size
inCapsuleDataSize: "4096"
# -- Max I/O size (bytes)
maxIoSize: "131072"
# -- I/O unit size (bytes)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need this at seperate places? Why not common?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its more structured this way ie separate setting for rdma and tcp
earlier only setting for tcp were defined.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants